Automated conversion of two-dimensional hydrology vector models into valid three-dimensional hydrology vector models

ABSTRACT

A system for automated conversion of two-dimensional hydrology vector models into valid three-dimensional hydrology vector models, comprising a vector extraction engine that retrieves vectors from, and sends vectors to, a vector storage, a DSM server that retrieves a DSM from a DSM storage and computes a DSM from stereo disparity measurements of a stereo pair retrieved from a raster storage, and a rendering engine that provides visual representations of images for review by a human user, and a method for automated hydrology vector model development utilizing the system of the invention.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of, and priority to, U.S. provisional patent application Ser. No. 62/019,878, titled “ENHANCEMENTS FOR AUTOMATED HYDROLOGY MODEL DEVELOPMENT” and filed on Jul. 1, 2014, the entire specification of which is incorporated herein by reference in its entirety.

BACKGROUND OF THE INVENTION

Field of the Art

The disclosure relates to the field of image processing and linear feature extraction, and more particularly to the field of extracting three-dimensional hydrology vector models from remotely-sensed imagery.

Discussion of the State of the Art

In the art of linear feature extraction, ROADTRACKER™ and similar tools enable automated bulk extraction and semi-automated point-to-point extraction of two-dimensional linear feature vectors from remotely-sensed imagery. Extractions by these tools are image-based, meaning image content automatically influences the trajectories of the extracted vectors. In semi-automated extraction, the image raster is displayed in a viewer and extraction is partially guided by user mouse clicks placed along a desired linear feature. Tools like ROADTRACKER™ can be used to perform two-dimensional extraction of, among other things, single-line drainages (the centerline vectors of narrow streams), double-line drainages (the two side vectors of rivers), and the boundaries of water bodies, and includes automatic smoothing of the extracted vectors and automatic topology cleaning of the vectors (elimination of gaps (under-shoots) and dangles (over-shoots) where vectors are intended to be perfectly incident to one another.) In this manner, a two-dimensional hydrology vector model for a raster image may be constructed.

What is needed is an automated way to convert a two-dimensional hydrology vector model into a corresponding three-dimensional hydrology vector model where the latter is geometrically consistent with the physics of real-world hydrology, i.e., lake boundaries are level, corresponding points on opposite sides of a river are at the same altitude, and water flow is monotone decreasing in altitude.

SUMMARY OF THE INVENTION

Accordingly, the inventor has conceived and reduced to practice, in a preferred embodiment of the invention, a system and method for automatically converting a two-dimensional hydrology vector model into a three-dimensional hydrology vector model where the latter is geometrically consistent with the physics of real-world hydrology, i.e., lake boundaries are level, corresponding points on opposite sides of a river are at the same altitude, and water flow is monotone decreasing in altitude. The three-dimensional vectors are expressed in the X, Y, Z coordinates of object space.

According to a preferred embodiment of the invention, a system for automatically converting a two-dimensional hydrology vector model into a three-dimensional hydrology vector model that is geometrically consistent with the physics of real-world hydrology comprising a vector server stored and operating on a network-connected computing device, a raster server stored and operating on a network-connected computing device, a digital surface model (DSM) server stored and operating on a network-connected computing device, a vector extraction engine stored and operating on a network-connected computing device, and a rendering engine stored and operating on a network-connected computing device, is disclosed.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

The accompanying drawings illustrate several embodiments of the invention and, together with the description, serve to explain the principles of the invention according to the embodiments. It will be appreciated by one skilled in the art that the particular embodiments illustrated in the drawings are merely exemplary, and are not to be considered as limiting of the scope of the invention or the claims herein in any way.

FIG. 1 is a block diagram illustrating an exemplary hardware architecture of a computing device used in an embodiment of the invention.

FIG. 2 is a block diagram illustrating an exemplary logical architecture for a client device, according to an embodiment of the invention.

FIG. 3 is a block diagram showing an exemplary architectural arrangement of clients, servers, and external services, according to an embodiment of the invention.

FIG. 4 is another block diagram illustrating an exemplary hardware architecture of a computing device used in various embodiments of the invention.

FIG. 5 is a block diagram illustrating an exemplary system architecture for automated conversion of two-dimensional hydrology vector models into valid three-dimensional hydrology vector models, according to a preferred embodiment of the invention.

DETAILED DESCRIPTION

The inventor has conceived in a preferred embodiment of the invention, a system and method for automatic conversion of two-dimensional hydrology vector models into three-dimensional hydrology vector models, where the latter are geometrically consistent with the physical behavior of real-world hydrology. The three-dimensional vectors are expressed in the X, Y, Z coordinates of object space.

One or more different inventions may be described in the present application. Further, for one or more of the inventions described herein, numerous alternative embodiments may be described; it should be appreciated that these are presented for illustrative purposes only and are not limiting of the inventions contained herein or the claims presented herein in any way. One or more of the inventions may be widely applicable to numerous embodiments, as may be readily apparent from the disclosure. In general, embodiments are described in sufficient detail to enable those skilled in the art to practice one or more of the inventions, and it should be appreciated that other embodiments may be utilized and that structural, logical, software, electrical and other changes may be made without departing from the scope of the particular inventions. Accordingly, one skilled in the art will recognize that one or more of the inventions may be practiced with various modifications and alterations. Particular features of one or more of the inventions described herein may be described with reference to one or more particular embodiments or figures that form a part of the present disclosure, and in which are shown, by way of illustration, specific embodiments of one or more of the inventions. It should be appreciated, however, that such features are not limited to usage in the one or more particular embodiments or figures with reference to which they are described. The present disclosure is neither a literal description of all embodiments of one or more of the inventions nor a listing of features of one or more of the inventions that must be present in all embodiments.

Headings of sections provided in this patent application and the title of this patent application are for convenience only, and are not to be taken as limiting the disclosure in any way.

Devices that are in communication with each other need not be in continuous communication with each other, unless expressly specified otherwise. In addition, devices that are in communication with each other may communicate directly or indirectly through one or more communication means or intermediaries, logical or physical.

A description of an embodiment with several components in communication with each other does not imply that all such components are required. To the contrary, a variety of optional components may be described to illustrate a wide variety of possible embodiments of one or more of the inventions and in order to more fully illustrate one or more aspects of the inventions. Similarly, although process steps, method steps, algorithms or the like may be described in a sequential order, such processes, methods and algorithms may generally be configured to work in alternate orders, unless specifically stated to the contrary. In other words, any sequence or order of steps that may be described in this patent application does not, in and of itself, indicate a requirement that the steps be performed in that order. The steps of described processes may be performed in any order practical. Further, some steps may be performed simultaneously despite being described or implied as occurring non-simultaneously (e.g., because one step is described after the other step). Moreover, the illustration of a process by its depiction in a drawing does not imply that the illustrated process is exclusive of other variations and modifications thereto, does not imply that the illustrated process or any of its steps are necessary to one or more of the invention(s), and does not imply that the illustrated process is preferred. Also, steps are generally described once per embodiment, but this does not mean they must occur once, or that they may only occur once each time a process, method, or algorithm is carried out or executed. Some steps may be omitted in some embodiments or some occurrences, or some steps may be executed more than once in a given embodiment or occurrence.

When a single device or article is described herein, it will be readily apparent that more than one device or article may be used in place of a single device or article. Similarly, where more than one device or article is described herein, it will be readily apparent that a single device or article may be used in place of the more than one device or article.

The functionality or the features of a device may be alternatively embodied by one or more other devices that are not explicitly described as having such functionality or features. Thus, other embodiments of one or more of the inventions need not include the device itself.

Techniques and mechanisms described or referenced herein will sometimes be described in singular form for clarity. However, it should be appreciated that particular embodiments may include multiple iterations of a technique or multiple instantiations of a mechanism unless noted otherwise. Process descriptions or blocks in figures should be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of embodiments of the present invention in which, for example, functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those having ordinary skill in the art.

Hardware Architecture

Generally, the techniques disclosed herein may be implemented on hardware or a combination of software and hardware. For example, they may be implemented in an operating system kernel, in a separate user process, in a library package bound into network applications, on a specially constructed machine, on an application-specific integrated circuit (ASIC), or on a network interface card.

Software/hardware hybrid implementations of at least some of the embodiments disclosed herein may be implemented on a programmable network-resident machine (which should be understood to include intermittently connected network-aware machines) selectively activated or reconfigured by a computer program stored in memory. Such network devices may have multiple network interfaces that may be configured or designed to utilize different types of network communication protocols. A general architecture for some of these machines may be described herein in order to illustrate one or more exemplary means by which a given unit of functionality may be implemented. According to specific embodiments, at least some of the features or functionalities of the various embodiments disclosed herein may be implemented on one or more general-purpose computers associated with one or more networks, such as for example an end-user computer system, a client computer, a network server or other server system, a mobile computing device (e.g., tablet computing device, mobile phone, smartphone, laptop, or other appropriate computing device), a consumer electronic device, a music player, or any other suitable electronic device, router, switch, or other suitable device, or any combination thereof. In at least some embodiments, at least some of the features or functionalities of the various embodiments disclosed herein may be implemented in one or more virtualized computing environments (e.g., network computing clouds, virtual machines hosted on one or more physical computing machines, or other appropriate virtual environments).

Referring now to FIG. 1, there is shown a block diagram depicting an exemplary computing device 100 suitable for implementing at least a portion of the features or functionalities disclosed herein. Computing device 100 may be, for example, any one of the computing machines listed in the previous paragraph, or indeed any other electronic device capable of executing software- or hardware-based instructions according to one or more programs stored in memory. Computing device 100 may be adapted to communicate with a plurality of other computing devices, such as clients or servers, over communications networks such as a wide area network a metropolitan area network, a local area network, a wireless network, the Internet, or any other network, using known protocols for such communication, whether wireless or wired.

In one embodiment, computing device 100 includes one or more central processing units (CPU) 102, one or more interfaces 110, and one or more busses 106 (such as a peripheral component interconnect (PCI) bus). When acting under the control of appropriate software or firmware, CPU 102 may be responsible for implementing specific functions associated with the functions of a specifically configured computing device or machine. For example, in at least one embodiment, a computing device 100 may be configured or designed to function as a server system utilizing CPU 102, local memory 101 and/or remote memory 120, and interface(s) 110. In at least one embodiment, CPU 102 may be caused to perform one or more of the different types of functions and/or operations under the control of software modules or components, which for example, may include an operating system and any appropriate applications software, drivers, and the like.

CPU 102 may include one or more processors 103 such as, for example, a processor from one of the Intel, ARM, Qualcomm, and AMD families of microprocessors. In some embodiments, processors 103 may include specially designed hardware such as application-specific integrated circuits (ASICs), electrically erasable programmable read-only memories (EEPROMs), field-programmable gate arrays (FPGAs), and so forth, for controlling operations of computing device 100. In a specific embodiment, a local memory 101 (such as non-volatile random access memory (RAM) and/or read-only memory (ROM), including for example one or more levels of cached memory) may also form part of CPU 102. However, there are many different ways in which memory may be coupled to system 100. Memory 101 may be used for a variety of purposes such as, for example, caching and/or storing data, programming instructions, and the like. It should be further appreciated that CPU 102 may be one of a variety of system-on-a-chip (SOC) type hardware that may include additional hardware such as memory or graphics processing chips, such as a Qualcomm SNAPDRAGON™ or Samsung EXYNOS™ CPU as are becoming increasingly common in the art, such as for use in mobile devices or integrated devices.

As used herein, the term “processor” is not limited merely to those integrated circuits referred to in the art as a processor, a mobile processor, or a microprocessor, but broadly refers to a microcontroller, a microcomputer, a programmable logic controller, an application-specific integrated circuit, and any other programmable circuit.

In one embodiment, interfaces 110 are provided as network interface cards (NICs). Generally, NICs control the sending and receiving of data packets over a computer network; other types of interfaces 110 may for example support other peripherals used with computing device 100. Among the interfaces that may be provided are Ethernet interfaces, frame relay interfaces, cable interfaces, DSL interfaces, token ring interfaces, graphics interfaces, and the like. In addition, various types of interfaces may be provided such as, for example, universal serial bus (USB), Serial, Ethernet, FIREWIRE™, THUNDERBOLT™, PCI, parallel, radio frequency (RF), BLUETOOTH™, near-field communications (e.g., using near-field magnetics), 802.11 (WiFi), frame relay, TCP/IP, ISDN, fast Ethernet interfaces, Gigabit Ethernet interfaces, Serial ATA (SATA) or external SATA (ESATA) interfaces, high-definition multimedia interface (HDMI), digital visual interface (DVI), analog or digital audio interfaces, asynchronous transfer mode (ATM) interfaces, high-speed serial interface (HSSI) interfaces, Point of Sale (POS) interfaces, fiber data distributed interfaces (FDDIs), and the like. Generally, such interfaces 110 may include physical ports appropriate for communication with appropriate media. In some cases, they may also include an independent processor (such as a dedicated audio or video processor, as is common in the art for high-fidelity A/V hardware interfaces) and, in some instances, volatile and/or non-volatile memory (e.g., RAM).

Although the system shown in FIG. 1 illustrates one specific architecture for a computing device 100 for implementing one or more of the inventions described herein, it is by no means the only device architecture on which at least a portion of the features and techniques described herein may be implemented. For example, architectures having one or any number of processors 103 may be used, and such processors 103 may be present in a single device or distributed among any number of devices. In one embodiment, a single processor 103 handles communications as well as routing computations, while in other embodiments a separate dedicated communications processor may be provided. In various embodiments, different types of features or functionalities may be implemented in a system according to the invention that includes a client device (such as a tablet device or smartphone running client software) and server systems (such as a server system described in more detail below).

Regardless of network device configuration, the system of the present invention may employ one or more memories or memory modules (such as, for example, remote memory block 120 and local memory 101) configured to store data, program instructions for the general-purpose network operations, or other information relating to the functionality of the embodiments described herein (or any combinations of the above). Program instructions may control execution of or comprise an operating system and/or one or more applications, for example. Memory 120 or memories 101, 120 may also be configured to store data structures, configuration data, encryption data, historical system operations information, or any other specific or generic non-program information described herein.

Because such information and program instructions may be employed to implement one or more systems or methods described herein, at least some network device embodiments may include nontransitory machine-readable storage media, which, for example, may be configured or designed to store program instructions, state information, and the like for performing various operations described herein. Examples of such nontransitory machine-readable storage media include, but are not limited to, magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROM disks; magneto-optical media such as optical disks, and hardware devices that are specially configured to store and perform program instructions, such as read-only memory devices (ROM), flash memory (as is common in mobile devices and integrated systems), solid state drives (SSD) and “hybrid SSD” storage drives that may combine physical components of solid state and hard disk drives in a single hardware device (as are becoming increasingly common in the art with regard to personal computers), memristor memory, random access memory (RAM), and the like. It should be appreciated that such storage means may be integral and non-removable (such as RAM hardware modules that may be soldered onto a motherboard or otherwise integrated into an electronic device), or they may be removable such as swappable flash memory modules (such as “thumb drives” or other removable media designed for rapidly exchanging physical storage devices), “hot-swappable” hard disk drives or solid state drives, removable optical storage discs, or other such removable media, and that such integral and removable storage media may be utilized interchangeably. Examples of program instructions include both object code, such as may be produced by a compiler, machine code, such as may be produced by an assembler or a linker, byte code, such as may be generated by for example a Java™ compiler and may be executed using a Java virtual machine or equivalent, or files containing higher level code that may be executed by the computer using an interpreter (for example, scripts written in Python, Perl, Ruby, Groovy, or any other scripting language).

In some embodiments, systems according to the present invention may be implemented on a standalone computing system. Referring now to FIG. 2, there is shown a block diagram depicting a typical exemplary architecture of one or more embodiments or components thereof on a standalone computing system. Computing device 200 includes processors 210 that may run software that carry out one or more functions or applications of embodiments of the invention, such as for example a client application 230. Processors 210 may carry out computing instructions under control of an operating system 220 such as, for example, a version of Microsoft's WINDOWS™ operating system, Apple's Mac OS/X or iOS operating systems, some variety of the Linux operating system, Google's ANDROID™ operating system, or the like. In many cases, one or more shared services 225 may be operable in system 200, and may be useful for providing common services to client applications 230. Services 225 may for example be WINDOWS™ services, user-space common services in a Linux environment, or any other type of common service architecture used with operating system 210. Input devices 270 may be of any type suitable for receiving user input, including for example a keyboard, touchscreen, microphone (for example, for voice input), mouse, touchpad, trackball, or any combination thereof. Output devices 260 may be of any type suitable for providing output to one or more users, whether remote or local to system 200, and may include for example one or more screens for visual output, speakers, printers, or any combination thereof. Memory 240 may be random-access memory having any structure and architecture known in the art, for use by processors 210, for example to run software. Storage devices 250 may be any magnetic, optical, mechanical, memristor, or electrical storage device for storage of data in digital form (such as those described above, referring to FIG. 1). Examples of storage devices 250 include flash memory, magnetic hard drive, CD-ROM, and/or the like.

In some embodiments, systems of the present invention may be implemented on a distributed computing network, such as one having any number of clients and/or servers. Referring now to FIG. 3, there is shown a block diagram depicting an exemplary architecture 300 for implementing at least a portion of a system according to an embodiment of the invention on a distributed computing network. According to the embodiment, any number of clients 330 may be provided. Each client 330 may run software for implementing client-side portions of the present invention; clients may comprise a system 200 such as that illustrated in FIG. 2. In addition, any number of servers 320 may be provided for handling requests received from one or more clients 330. Clients 330 and servers 320 may communicate with one another via one or more electronic networks 310, which may be in various embodiments any of the Internet, a wide area network, a mobile telephony network (such as CDMA or GSM cellular networks), a wireless network (such as WiFi, Wimax, LTE, and so forth), or a local area network (or indeed any network topology known in the art; the invention does not prefer any one network topology over any other). Networks 310 may be implemented using any known network protocols, including for example wired and/or wireless protocols.

In addition, in some embodiments, servers 320 may call external services 370 when needed to obtain additional information, or to refer to additional data concerning a particular call. Communications with external services 370 may take place, for example, via one or more networks 310. In various embodiments, external services 370 may comprise web-enabled services or functionality related to or installed on the hardware device itself. For example, in an embodiment where client applications 230 are implemented on a smartphone or other electronic device, client applications 230 may obtain information stored in a server system 320 in the cloud or on an external service 370 deployed on one or more of a particular enterprise's or user's premises.

In some embodiments of the invention, clients 330 or servers 320 (or both) may make use of one or more specialized services or appliances that may be deployed locally or remotely across one or more networks 310. For example, one or more databases 340 may be used or referred to by one or more embodiments of the invention. It should be understood by one having ordinary skill in the art that databases 340 may be arranged in a wide variety of architectures and using a wide variety of data access and manipulation means. For example, in various embodiments one or more databases 340 may comprise a relational database system using a structured query language (SQL), while others may comprise an alternative data storage technology such as those referred to in the art as “NoSQL” (for example, Hadoop Cassandra, Google BigTable, and so forth). In some embodiments, variant database architectures such as column-oriented databases, in-memory databases, clustered databases, distributed databases, or even flat file data repositories may be used according to the invention. It will be appreciated by one having ordinary skill in the art that any combination of known or future database technologies may be used as appropriate, unless a specific database technology or a specific arrangement of components is specified for a particular embodiment herein. Moreover, it should be appreciated that the term “database” as used herein may refer to a physical database machine, a cluster of machines acting as a single database system, or a logical database within an overall database management system. Unless a specific meaning is specified for a given use of the term “database”, it should be construed to mean any of these senses of the word, all of which are understood as a plain meaning of the term “database” by those having ordinary skill in the art.

Similarly, most embodiments of the invention may make use of one or more security systems 360 and configuration systems 350. Security and configuration management are common information technology (IT) and web functions, and some amount of each are generally associated with any IT or web systems. It should be understood by one having ordinary skill in the art that any configuration or security subsystems known in the art now or in the future may be used in conjunction with embodiments of the invention without limitation, unless a specific security 360 or configuration system 350 or approach is specifically required by the description of any specific embodiment.

FIG. 4 shows an exemplary overview of a computer system 400 as may be used in any of the various locations throughout the system. It is exemplary of any computer that may execute code to process data. Various modifications and changes may be made to computer system 400 without departing from the broader scope of the system and method disclosed herein. CPU 401 is connected to bus 402, to which bus is also connected memory 403, nonvolatile memory 404, display 407, I/O unit 408, and network interface card (NIC) 413. I/O unit 408 may, typically, be connected to keyboard 409, pointing device 410, hard disk 412, and real-time clock 411. NIC 413 connects to network 414, which may be the Internet or a local network, which local network may or may not have connections to the Internet. Also shown as part of system 400 is power supply unit 405 connected, in this example, to ac supply 406. Not shown are batteries that could be present, and many other devices and modifications that are well known but are not applicable to the specific novel functions of the current system and method disclosed herein. It should be appreciated that some or all components illustrated may be combined, such as in various integrated applications (for example, Qualcomm or Samsung SOC-based devices), or whenever it may be appropriate to combine multiple capabilities or functions into a single hardware device (for instance, in mobile devices such as smartphones, video game consoles, in-vehicle computer systems such as navigation or multimedia systems in automobiles, or other integrated hardware devices).

In various embodiments, functionality for implementing systems or methods of the present invention may be distributed among any number of client and/or server components. For example, various software modules may be implemented for performing various functions in connection with the present invention, and such modules may be variously implemented to run on server and/or client components.

Conceptual Architecture

FIG. 5 is a block diagram illustrating an exemplary system architecture 500 for automatically converting a two-dimensional hydrology vector model into a three-dimensional hydrology vector model that is geometrically consistent with the physics of real-world hydrology, and viewing the results, according to a preferred embodiment of the invention. According to the embodiment, a vector extraction engine 501 may retrieve vectors from, and send vectors to, a vector storage such as a vector database 502 or other data storage means (such as, for example, integral or removable hardware-based storage such as a hard disk drive, or software-based storage schema common in the art); a raster database 503 may provide raster images from a raster storage, for example such as satellite images or similar raster image data that depict an actual physical environment; a DSM server 508 may retrieve a DSM from a DSM storage 507, or may compute a DSM from the stereo disparity measurements of a stereo pair retrieved from a raster storage. Retrieved two-dimensional vectors and DSM may be provided to a vector extraction engine 501, which lifts the vectors into three dimensions and enforces geometric constraints, making the latter vectors consistent with the physics of real-world hydrology.

Vectors, rasters, and DSM may then be provided to a rendering engine 504, that may form a combined visualization, showing how the vectors relate to the rasters or DSM, such as may be presentable on a viewer 506 such as a display screen, for example, for review by a human user. Additionally, a user may interact with the presented visualization using a variety of input devices 505 such as (for example, including but not limited to) a computer mouse or keyboard to manipulate the visualization (e.g., zoom or pan). The three-dimensional extracted vectors may be further provided to vector extraction engine 501, for example, to store the vectors for future reference.

It should be appreciated that according to the embodiment, various means of connection or communication between the components of a system 500 may be utilized according to the invention interchangeably or simultaneously, such as for example a direct, physical data connection (such as via a data cable or similar physical means), a software-based connection such as via an application programming interface (API) or other software communication means (such as may be suitable, for example, in arrangements where multiple system components may operate on a single hardware device such as a computing server or workstation), or any of a variety of network connections such as via the Internet or other data communications network. It should therefore be appreciated that the connections shown are exemplary in nature and represent only a selection of possible arrangements, and that alternate or additional connections may be utilized according to the invention.

Detailed Description of Exemplary Embodiments

The vector extraction engine takes as input a two-dimensional hydrology vector model (expressed in the X, Y coordinates of object space) and a DSM (expressed in the X, Y, Z coordinates of object space) and computes a three-dimensional hydrology vector model (expressed in the X, Y, Z coordinates of object space) that is geometrically consistent with the physics of real-world hydrology, namely: lake boundaries are level, corresponding points on opposite sides of a river are at the same altitude, and water flow is monotone decreasing in altitude.

In a preferred embodiment, the vector extraction engine first automatically projects all two-dimensional hydrology vectors vertically (in the Z direction) to the DSM. Care is taken to ensure that the inter-connection topology among the vectors that existed in two dimensions is maintained in the three-dimensional projection.

For each two-dimensional lake boundary vector, in a preferred embodiment, the vector extraction engine takes median Z-value of the initially projected lake boundary vector as the common Z-value for all the points of the final three-dimensional lake boundary vector. Any three-dimensional vectors that were initially incident to the projected lake boundary vector are automatically adjusted near their terminals to maintain the incidence with the final three-dimensional lake boundary vector.

For any pair of two-dimensional side vectors U and V of a river, in a preferred embodiment, the vector extraction engine automatically computes the two-dimensional centerline vector W between U and V, and then automatically projects W vertically (in the Z direction) to the DSM resulting in the three-dimensional vector W*. Let S_(W) denote the unique infinite vertical surface containing W. Similarly define S_(U) and S_(V). The vector extraction engine automatically takes the projected vector W* and projects it normally from surface S_(W) onto surfaces S_(U) and S_(V). These new vectors on S_(U) and S_(V) are taken as the final three-dimensional vectors corresponding to U and V, respectively. Any three-dimensional vectors that were incident to the initial projections of U and V are automatically adjusted near their terminals to maintain the incidence with the final three-dimensional versions of U and V.

Let W* denote a projected (three-dimensional) single-line drainage vector. Let p and q denote the endpoints of W*, where the Z-value of p is greater than that of q. To enforce monotonicity of Z-profile on W*, in a preferred embodiment, the vector extraction engine employs one of several existing known algorithms to create a new vector W** from p to q that is monotone decreasing in Z and as close as possible to W* according to some measure of closeness. These algorithms will be known to someone familiar in the art. The vector extraction engine automatically indicates (perhaps by depicting an arrow on the resulting vector in the viewer) that the drainage direction goes from endpoint p (with higher Z-value) to endpoint q (with lower Z-value).

In a preferred embodiment, the vector extraction engine automatically affects the transformation from W* to W** (as described previously) for the two-dimensional centerline vector W of a river, whose two-dimensional side vectors are denoted U and V, before constructing the final three-dimensional versions of U and V (as described previously). In other words, the three-dimensional versions of U and V are constructed from W** instead of W*.

Finally in a preferred embodiment, the vector extraction engine smoothes all three-dimensional single-line and double-line drainage vectors in the Z coordinate.

The skilled person will be aware of a range of possible modifications of the various embodiments described above. Accordingly, the present invention is defined by the claims and their equivalents. 

What is claimed is:
 1. A system for automated conversion of two-dimensional hydrology vector models into valid three-dimensional hydrology vector models, comprising: a vector extraction engine comprising a plurality of programming instructions stored in a memory and operating on a processor of a computing device, and configured to retrieve vectors from, and send vectors to, a vector storage such as a vector database; a DSM (digital surface model) server comprising a plurality of programming instructions stored in a memory and operating on a processor of a computing device, and configured to retrieve a DSM from a DSM storage, and further configured to compute a DSM from stereo disparity measurements of a stereo pair retrieved from a raster storage; a rendering engine comprising a plurality of programming instructions stored in a memory and operating on a processor of a computing device, and configured to receive a plurality of data from other components of the system and create visual representations in the form of three dimensional hydrology vector models of the data for review by a human user.
 2. The system of claim 1, further comprising a database computer comprising program code stored in a memory and adapted to store and provide information for other components of the system.
 3. The system of claim 1, further comprising a viewer device adapted to receive information from other components of the system and present the information for review by a human user.
 4. The system of claim 1, further comprising a plurality of input devices adapted to receive input from a human user and provide the results of the input to other components of the system.
 5. A method for automated hydrology model development, comprising the steps of: receiving, at a hydrology vector server, a plurality of input images; extracting a plurality of hydrology vectors from at least a portion of the plurality of input images; algorithmically cleaning at least a portion of the hydrology vectors; enforcing vector attributes based at least in part on at least a portion of the hydrology vectors; and computing a hydrology graph model based at least in part on at least a portion of the vector attributes.
 6. The method of claim 5, further comprising the step of cleaning at least a portion of the plurality of hydrology vectors.
 7. The method of claim 6, wherein the cleaning is performed automatically by the hydrology vector server.
 8. The method of claim 6, wherein the cleaning is performed manually by a human user.
 9. The method of claim 5, further comprising the step of designating at least a portion of the hydrology vectors for use as feature vectors.
 10. The method of claim 9, wherein the designating is performed automatically by the hydrology vector server.
 11. The method of claim 9, wherein the designating is performed manually by a human user.
 12. The method of claim 5, further comprising the step of automatically enforcing vector monotonicity based at least in part on at least a portion of the vector attributes.
 13. The method of claim 12, wherein the hydrology vector graph model is based at least in part on at least a portion of the vector monotonicity.
 14. The method of claim 5, further comprising the step of providing the hydrology vector graph model as output.
 15. The method of claim 14, wherein the output is stored, in a database, for future reference.
 16. The method of claim 14, wherein the output is displayed on a display device for review or interaction by a human user. 